Architectural Design to Meet Stakeholder Requirements

Architectural design occupies a pivotal position in software engineering. It is during architectural design that crucial requirements such as performance, reliability, costs, etc., must be addressed. Yet the task of achieving these properties remains a difficult one. Senior architects with many years of experience have to make difficult choices to meet competing requirements. This task is made even more difficult with the shift in software engineering paradigm from monolithic, stand-alone, built-from-scratch systems to componentized, evolvable, standards-based, and product line oriented systems. Many well-established design strategies need to be reconsidered as new requirements such as evolvability, reusability, time-to-market, etc., are becoming more important. These requirements do not come from a single source, but result from negotiations among many stakeholders. A systematic framework is needed to help architects achieve quality requirements during architectural design. This paper outlines an approach that formulates architectural properties such as modifiability and performance as “softgoals” which are incrementally refined. Tradeoffs are made as conflicts and synergies are discovered. Architectural decisions are traced to stakeholders and their dependency relationships. Knowledge-based tool support for the process would provide guidance during design as well as records of design rationales to facilitate understanding and change management. 2 L. Chung, D. Gross & E. Yu